chore(deps): update all non-major dependencies #218
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
46eabef
to
f1b48e7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
24 times, most recently
from
5d6c993
to
6d5b608
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
b74ab93
to
cb94fcf
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
9 times, most recently
from
8376345
to
525b163
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
2cfcdfe
to
c2de67e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
f9afbc8
to
a1fca68
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
fcf771c
to
7383d61
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
e7febdb
to
ffc0159
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ffc0159
to
ca8f0e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.8.0->^3.11.2^19.5.0->^19.6.0^19.5.0->^19.6.0^1.1.2->^1.2.0^1.2.10->^1.2.17^1.2.9->^1.2.13^1.6.0->^1.6.1^1.5.6->^1.9.0^3.13.2->^3.14.1592^2.18.7->^2.19.2^8.5.5->^8.5.6^5.21.1->^5.22.0^22.7.9->^22.10.1^6.4.16->^6.4.17^4.14.4->^4.14.7^5.1.4->^5.2.1^0.0.19->^0.0.21^11.1.0->^11.3.0^11.1.0->^11.3.0^0.7.0->^0.7.1^7.4.2->^7.4.4^9.1.6->^9.1.7^1.11.12->^1.11.15>=20.18.0->>=20.18.122.10.0-alpine->22.11.0-alpine22.10.0-alpine->22.11.0-alpine^6.9.15->^6.9.16^3.13.2->^3.14.1592^0.5.0->^0.5.5^1.10.0->^1.11.29.12.1->9.14.4>=9.12.1->>=9.14.4^5.21.1->^5.22.0^1.9.7->^1.9.10^0.10.4->^0.11.3^2.5.4->^2.5.5^3.4.14->^3.4.15v3.1->v3.2^2.2.3->^2.3.3^4.14.4->^4.14.7^2.1.6->^2.1.10Release Notes
antfu/eslint-config (@antfu/eslint-config)
v3.11.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.11.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.11.0Compare Source
🐞 Bug Fixes
antfu/no-top-level-awaitfor Astro - by @kidonng in https://github.com/antfu/eslint-config/issues/638 (40ee7)View changes on GitHub
v3.10.0Compare Source
🚀 Features
perfectionistto v4 - by @antfu (667c4)View changes on GitHub
v3.9.2Compare Source
🚀 Features
View changes on GitHub
v3.9.1Compare Source
🐞 Bug Fixes
View changes on GitHub
conventional-changelog/commitlint (@commitlint/cli)
v19.6.0Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.6.0Compare Source
Note: Version bump only for package @commitlint/config-conventional
date-fns/tz (@date-fns/tz)
v1.2.0Fixed
setTimenot syncing the value to the internal date resulting in incorrect behavior #16, #24.nuxt/devtools (@nuxt/devtools)
v1.6.1Compare Source
Bug Fixes
Features
nuxt/icon (@nuxt/icon)
v1.9.0Compare Source
🚀 Features
View changes on GitHub
v1.8.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.8.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.8.0Compare Source
🚀 Features
Suspense- by @antfu (cbb24)View changes on GitHub
v1.7.6Compare Source
🐞 Bug Fixes
consolain server API, close #299 - by @antfu in https://github.com/nuxt/icon/issues/299 (e9dd4)View changes on GitHub
v1.7.5Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.7.4Compare Source
🚀 Features
🐞 Bug Fixes
consolain runtime, close #295 - by @antfu in https://github.com/nuxt/icon/issues/295 (36e38)View changes on GitHub
v1.7.3Compare Source
v1.7.2Compare Source
@iconify/vueby default (8b1d75c)addIconinstead ofaddCollection(fd46c6e)9b37e24)v1.7.1Compare Source
v1.7.0Compare Source
fe12434)fetchTimeoutto 1500 (ef5b8fd)13e5e7d)4e0593b)v1.6.1Compare Source
c09fdc7)v1.6.0Compare Source
52fbaa2)ee82b2e)799ee0b)v1.5.8Compare Source
2a619ac)v1.5.7Compare Source
7756d18)9d7c65e)31bbc52)1f3bf1f)nuxt/nuxt (@nuxt/kit)
v3.14.1592Compare Source
👉 Changelog
compare changes
🩹 Fixes
webpackbarwith support for rspack (#29823)dstto deduplicate templates when adding them (#29895)dstto invalidate modules (6cd3352de)changeevents (#29954)<NuxtWelcome>when building (#29956)💅 Refactors
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors
v3.14.159Compare Source
We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)
👉 Changelog
compare changes
🩹 Fixes
module.json(#29793)mllyto resolve module paths to avoid cjs fallback (#29799)webpack-dev-middleware(#29806)📖 Documentation
🏡 Chore
❤️ Contributors
v3.14.0Compare Source
👀 Highlights
Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the
unjsside with preparations for Nitro v3!)⚡️ Faster starts powered by
jitiLoading the nuxt config file, as well as modules and other build-time code, is now powered by
jitiv2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨📂 Shared folder for code and types shared with client/server
You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.
For this, we have a new
shared/folder (#28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.If needed you can use the new
#sharedalias which points to this folder.The shared folder is alongside your
server/folder. (If you're usingcompatibilityVersion: 4, this means it's not inside yourapp/folder.)🦀
rspackbuilderWe're excited to announce a new first-class Nuxt builder for
rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to useunpluginto make this possible.Let us know if you like it - and feel free to raise any issues you experience with it.
👉 To try it out, you can use this starter - or just install
@nuxt/rspack-builderand setbuilder: 'rspack'in your nuxt config file.✨ New composables
We have new
useResponseHeaderanduseRuntimeHookcomposables (#27131 and #29741).🔧 New module utilities
We now have a new
addServerTemplateutility (#29320) for adding virtual files for access inside nitro runtime routes.🚧 v4 changes
We've merged some changes which only take effect with
compatibilityVersion: 4, but which you can opt-into earlier.previously, if you had a component like
~/components/App/Header.vuethis would be visible in your devtools as<Header>. From v4 we ensure this is<AppHeader>, but it's opt-in to avoid breaking any manual<KeepAlive>you might have implemented. (#28745).Nuxt scans page metadata from your files, before calling
pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before callingpages:extend. Instead, we have a newpages:resolvedhook, which is called afterpages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMetatoafter-resolve, as it solves a number of bugs.🗺️ Roadmap to v3.15
They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):
✅ Upgrading
As usual, our recommendation for upgrading is to run:
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
👉 Changelog
compare changes
🚀 Enhancements
jiti(#29073)addServerTemplateutility (#29320)useResponseHeadercomposable ([#27131](https://redirect.github.com/nuxt/nuxt/pullConfiguration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.